Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update package.josn to match last seq release number #2674

Merged
merged 2 commits into from
Dec 16, 2019

Conversation

snide
Copy link
Contributor

@snide snide commented Dec 16, 2019

Summary

This PR does nothing but change the package.json version back to 17.2.0 so that the next release will be 17.2.1 (which I will kickoff on merge). For some reason during the revert hub-bub, it made a release against 17.1.3. Talking with @chandlerprall and @thompsongl we decided just producing a new release back on cadence (and properly notied things in the CL) was the easiest course of action.

Checklist

  • Checked in dark mode
  • Checked in mobile
  • Checked in IE11 and Firefox
  • Props have proper autodocs
  • Added documentation examples
  • Added or updated jest tests
  • Checked for breaking changes and labeled appropriately
  • Checked for accessibility including keyboard-only and screenreader modes
  • A changelog entry exists and is marked appropriately

Copy link
Contributor

@thompsongl thompsongl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you mean "so that the next release will be 17.3.1 17.2.1", but, yes 👍

@snide snide merged commit 1483751 into elastic:master Dec 16, 2019
@snide snide deleted the fix/eui_release branch December 16, 2019 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants